Use of replicated copies to improve database backup performance

ABSTRACT

A backup computing device detects an interruption while receiving a backup copy of a transaction log of a primary database and directs a secondary computing device to continue generation of the backup copy of the transaction log, based on the copy of the transaction log of the primary database. A primary computing device directs a secondary computing device to generate a backup copy of the data file and the primary computing device generates a backup copy of the transaction log, of a primary database. A primary computing device accesses a snapshot of a plurality of snapshots of a primary database, and generates a first portion of a backup copy of the database. The primary computing device directs a second computing device to generate a non-overlapping portion of the backup copy of the database based on a second snapshot of the plurality of snapshots.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of computingsystems, and more particularly to improvement of database backupperformance and efficiency.

There is a high level of dependence on access to current, accurate, andreliable data, in all areas of contemporary life, such as of commerce,government, education, recreation, and health. Securing data againstdevice failure, network interruption, security threats, andunanticipated catastrophic events, requires practice of well-disciplinedbackup procedures and plans. The high level of dependence on data alsoplaces stringent demands on avoiding interruption of receiving andprocessing transactions. In some cases it may be necessary to receiveand process data transactions twenty-four hours a day, seven days aweek, throughout the year. This creates complications in backing up databy disrupting received transactions or risking changes to original dataduring backup processing.

SUMMARY

According to an embodiment of the present invention, a method forgenerating a backup copy of a transaction log of a database ispresented. A backup computing device detects an interruption whilereceiving a backup copy of a transaction log of a primary database froma primary computing device, and the backup computing device directs asecondary computing device to continue generation of the backup copy ofthe transaction log and identifies a last transaction of the transactionlog received prior to detection of the interruption. The secondarycomputing device has access to a copy of the transaction log of theprimary database.

According to another embodiment of the present invention, a method ofgenerating a backup copy of a database is presented. Responding to adirection to produce a backup copy of a primary database, in which theprimary database includes a data file and a transaction log, a primarycomputing device directs a secondary computing device to generate abackup copy of the data file. The primary computing device generates abackup copy of the transaction log, and the primary computing devicesends the backup copy of the transaction log to a backup computingdevice.

According to another embodiment of the present invention a method forbacking up a database is presented. The primary computing device directsa second computing device to generate a non-overlapping portion of thebackup copy of the primary database, based on a corresponding portion ofa second snapshot of the plurality of snapshots, and the primarycomputing device sends the first portion of the backup copy to thebackup computing device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed computerprocessing environment, in accordance with one embodiment of the presentinvention.

FIG. 2 is a flowchart of a hot-transfer backup program, in accordancewith an embodiment of the present invention.

FIG. 3 is a flowchart illustrating operational steps of a simultaneousbackup program, operating on a primary data managing server within thedistributed computer processing environment of FIG. 1, in accordancewith an embodiment of the present invention.

FIG. 4 is a flowchart illustrating operational steps of a parallelbackup program, operating on a primary database server within thedistributed computer processing environment of FIG. 1, in accordancewith an embodiment of the present invention.

FIG. 5 depicts a block diagram of components of a database servercapable of operating the transfer backup program, the simultaneousbackup program, and the parallel backup program, in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

Embodiments in accordance with the present invention recognize thatgenerating backup copies of data, such as data found in databases,sometimes requires interruption of transaction activity by the computingdevice recording and performing transactional updates to the database.Such interruptions may cause impacts ranging from poor performance ofthe transaction handling server, to total unavailability of the serverduring backup generation. Embodiments of the present invention providebackup techniques that make use of redundant data management systems,for example a primary data management system that includes a primarydatabase server, a primary storage device, and a primary database, and asecondary data management system, which includes similar correspondingsecondary components. In embodiments of the present invention, backupcopies are received by a backup computing device, for example a backupserver, which may receive, perform, and send instructions associatedwith the generation of a backup copy of the database.

Embodiments use both the primary and secondary database servers toreduce the time required to generate backup copies of the database andreduce performance impacts. Embodiments also recognize that usingidentical sources of data for each computing device used to generate thebackup copy, avoids duplication or loss of data in the backup copy.

Some embodiments of the present invention use instructions sent to asecondary computing device to continue the generation of a backup copyof a transaction log, which has been interrupted while being performedby a primary computing device. The secondary computing device continuesthe generation of the backup copy of the transaction log, based on acopy of the transaction log received from the primary computing deviceprior to the interruption.

Other embodiments of the present invention use both a primary computingdevice, associated with a primary database, and a secondary computingdevice, associated with a secondary database that is substantially acopy of the primary database, to split the workload of generating abackup copy of the database. The primary and secondary databases eachinclude a data file and a transaction log. The backup of the data fileis generated by one computing device, and the transaction log backupcopy is generated by the other computing device, thus splitting theworkload of database backup activities.

In still other embodiments of the present invention a snapshot at apoint in time, is used as a reference to generate a backup copy of datastored in a logical structure, for example, a database on a storagedevice, such as a storage server. In one embodiment, the snapshot isgenerated by, and under the control of, storage hardware, which forexample may be a storage server of a data management environment,connected by a network to a server managing the operations andtransactions to be applied to a database. In other embodiments, thesnapshot may be created by a primary database server, connected to aprimary database, and copies of the snapshot are made by the primarydatabase server. In yet other embodiments, the snapshot may be createdby a secondary database server connected to a secondary database, whichis a replica of the primary database. The snapshot represents the stateof the stored data at the time of the generation of the snapshot. In oneembodiment of the present invention, a second snapshot is generated,such that the second snapshot is a snapshot of the first snapshot,resulting in identical snapshots having identical states of data withineach snapshot. The backup is generated by utilizing both a primarydatabase server and a redundant secondary database server, with eachserver generating a portion of the backup copy based on access to thesnapshot or snapshot of the snapshot, respectively. The combination ofthe portions of the backup copy results in a complete backup copy thatincludes the database data of the identical snapshots targeted forbackup.

The backup is performed more efficiently since redundant servers areused to each generate a portion of the backup, with the aggregate of thebackup portions including all the data from the snapshot of the primarydatabase to be backed up. Transaction processing is not interruptedsince the backup generation makes use of the snapshots of the primarydatabase to generate the backup copy.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram illustrating adistributed computer processing environment, generally designated 100,in accordance with an embodiment of the present invention. FIG. 1provides only an illustration of one implementation and does not implyany limitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironment may be made by those skilled in the art without departingfrom the scope of the invention as recited by the claims.

FIG. 1 includes primary database server 110, primary storage hardware120, which includes primary database 125, secondary database server 130,secondary storage hardware 135, which includes secondary database 140,and backup server 145, all interconnected through network 150. Primarydatabase server 110 is depicted as including transfer backup program200, simultaneous backup program 300, and parallel backup program 400.Secondary database server 130 receives transaction logs, such astransaction logs 162 and 164, and sends the transaction logs tosecondary storage hardware 135 to apply the transactions to database140. The aggregate transaction log (not shown), for secondary database140 is included in secondary storage hardware 135. In some embodimentsof the present invention, secondary database server 130 may includeportions of transfer backup program 200, simultaneous backup program300, and parallel backup program 400, used to complete processing of thebackup copy of the database (not shown). Similarly, in some embodiments,backup server 145 may include portions of transfer backup program 200,simultaneous backup program 300, and parallel backup program 400, toperform backup operations based on events detected by backup server 145(not shown). Network 150 is depicted as including transaction log 168,which is representative of network 150 providing a pathway for thein-process transmission of transaction log 168 from primary transactionserver 110 to secondary transaction server 130.

Network 150 can be, for example, a local area network (LAN), atelecommunications network, a wide area network (WAN), such as theInternet, a virtual local area network (VLAN), or any combination thatcan include wired, wireless, or fiber optic connections. In general,network 150 can be any combination of connections and protocols thatwill support communications between primary database server 110,secondary database server 130, backup server 145, and the othercomponents of distributed computer processing environment 100, inaccordance with embodiments of the present invention.

Backup server 145, is connected to the devices and resources ofdistributed computer processing environment 100 by network 150 and isoften positioned at a different physical location than primary databaseserver 110 and secondary database server 130. Backup server 145 includescomponents enabling the receipt and storage of backup copies of primarydatabase 125 and backup copies of the aggregate of individualtransaction logs, which contain a pre-determined amount of transactioninformation, hereafter the aggregate of the multiple transaction logs isreferred to as the aggregate transaction log. In some embodiments of thepresent invention, backup server 145 receives a backup of primarydatabase 125 from secondary database server 130, and a backup copy ofthe most current transaction log from primary database server 110, as aresult of dividing backup workload between the two servers. In oneembodiment of the present invention, backup server 145 may includeportions of transfer backup program 200, simultaneous backup program300, and parallel backup program 400, and may receive instructions fromprimary database server 110 to perform the portions of the programs.

Backup server 145 may be a management server, a blade server, a webserver, a mobile computing device, or any other electronic device orcomputing system capable of receiving and sending data, and performingcomputer-readable program instructions. In other embodiments, backupserver 145 may represent a server computing system utilizing multiplecomputers as a server system, such as in a cloud computing environment.In another embodiment, backup server 145 may be a laptop computer, atablet computer, a netbook computer, a personal computer (PC), a desktopcomputer, or any programmable electronic device capable of communicatingwith primary database server 110 and secondary database server 130, vianetwork 150. In another embodiment, backup server 145 represents acomputing system utilizing clustered computers and components (e.g.,database server computer, application server computers, etc.) that actas a single pool of seamless resources when accessed within distributedcomputer processing environment 100. Backup server 145 may includeinternal and external hardware components, as depicted and describedwith reference to FIG. 5.

In other embodiments of the present invention, backup server 145receives a portion of a backup copy that is generated from a snapshot ofprimary database 125 from primary database server 110, and the remainingportion of the backup copy is generated by secondary database server130, from a snapshot of the snapshot of primary database 125. Similarly,a backup copy of the transaction log may be generated from a snapshot ofthe transaction log from primary database server 110. A portion of thebackup copy of the transaction log is generated by primary databaseserver 110 from a snapshot of the transaction log, and the remainingportion of the backup copy of the transaction log is generated bysecondary database server 130, from a snapshot of the snapshot of thetransaction log of primary database server 110.

Secondary storage hardware 135 is connected to secondary database server130, and includes secondary database 140, and transaction logs 162 and164. Secondary storage hardware 135 includes storage and computingprocessor components that support transaction log updates from secondarydatabase server 130 to secondary database 140. Secondary storagehardware 135 receives transaction log updates, such as transaction logs162 and 164, from secondary database server 130, which are applied tosecondary database 140. In one embodiment of the present invention,secondary storage hardware 135 is enabled to generate a snapshot of thedata file of secondary database 140 and the aggregate transaction logfor secondary database 140, in response to receiving instructions to doso from primary database server 110 or secondary database server 130. Inanother embodiment, secondary storage hardware 135 may use streamingdata to produce a backup. In other embodiments, primary database server110 and secondary database server 130 may share the same storagehardware, with their respective data stored separately on the samestorage hardware. Secondary storage hardware 135 may include internaland external computer components described in more detail with respectto FIG. 5.

Secondary database 140 is a hot-copy replica of primary database 125,and includes redundant data of primary database 125 when transactionlogs sent to secondary database server 130 have been applied to updatesecondary database 140. As a replica of primary database 125, secondarydatabase 140 includes the data of primary database 125 other thantransactions from the current segment of the aggregate transaction logthat has not been send to secondary database server 130 to apply tosecondary database 140. Primary database 125 and secondary database 140differ only by the transactions that have been applied to primarydatabase 125, but have not yet been sent to secondary database server130 and applied to secondary database 140. When the generation of abackup copy of the aggregate transaction log of primary database 125 isinterrupted or fails, the generation of the backup copy of the aggregatetransaction log may continue by instructions that direct secondarydatabase server 130 to continue the generation of the transaction logbackup copy based on the copies of transaction logs received bysecondary database server 130 from primary database server 110.

Secondary database server 130 receives transaction logs from primarydatabase server 110 and processes the transaction log updates, sendingthe updates to secondary storage hardware 135, which applies the updatesto secondary database 140. In one embodiment of the present invention,transactions received by primary database server 110, are written to atransaction log, and then applied to primary database 125. Transactionscontinue to be written to the transaction log until a pre-determinedfile size is attained, for example 1 megabyte (MB). The transaction logcontaining a full file size of transactions is sent from primarydatabase server 110 to secondary database server 130, and thetransactions of the received transaction log, for example transactionlog 162, are applied to secondary database 140. In this manner,secondary database 140 includes all transaction applied to primarydatabase 125, except for the current transactions of the transaction logthat has yet to reach the pre-determined memory capacity oftransactions, and has not been sent to secondary database server 130.

In embodiments of the present invention, secondary database server 130performs activities supporting the backup techniques described herein.In some embodiments secondary database server 130 executes instructionsreceived from applications running on primary database server 110. Inother embodiments, secondary database server may receive instructionsfrom backup server 145 to perform backup tasks when triggering eventsare detected. Instructions include information enabling the receivingdevice to perform one or more activities of a transfer backup program200, simultaneous backup program 300, and parallel backup program 400.In still other embodiments, secondary database server 130 may performportions of programs 200, 300, and 400, installed on secondary databaseserver 130, in response to receiving initiation messages from othercomputing devices, for example primary database server 110 or backupserver 145.

In one embodiment of the present invention, secondary database server130 receives instructions from primary database server 110 at theinitiation of generating the backup copy. If the generation of thebackup copy by primary database server 110 is interrupted or fails,secondary database server 130 continues generating a backup copy of thetransaction log based on a copy of the transaction log in the secondarydatabase, and receiving an initiation message from backup server 145,which detects the interruption, to continue generation of the backupcopy from the transaction sequence at which the backup copy generationwas interrupted.

In another embodiment of the present invention, backup server 145receives portions of transfer backup program 200 from primary databaseserver at the initiation of the backup copy. Backup server 145 executestransfer backup program 200 based on detection of an interruption ofbackup data from primary database server 110. In response to the backupfailing to continue from primary database server 110 in a pre-definedamount of time, backup server 145 instructs secondary database server130 to continue generating the backup copy of the transaction logs.Backup server 145 indicates the last transaction received from primarydatabase server 110 and secondary database server 130 begins generationof the backup copy of the transaction log at the next transaction in thesequence.

In another embodiment of the present invention, to more efficientlygenerate a backup copy of database data, secondary database server 130receives instruction from simultaneous backup program 300, operating onprimary database server 110, to generate a backup copy of the data fileof secondary database 140, which is a copy of primary database 125except for the most recent transactions that have not yet been sent tosecondary database server 130 and applied to secondary database 140.Generating a copy of secondary database 140 by secondary database server130 does not impact the availability or performance of primary database125 to receive and process transactions. In this embodiment, primarydatabase server 110 generates a copy of the aggregate transaction log,which is typically smaller in size and less demanding of processing timeand allows primary database server 110 to maintain high availabilitywhile a backup copy is performed. In other embodiments, primary databaseserver 110 generates a copy of the data file of primary database 125,and secondary database server 130 generates a backup copy of theaggregate transaction logs received from primary database server 110. Itshould be pointed out that although simultaneous backup program 300 isdepicted as being operated on primary database server 110, program 300may be operated by secondary database server 130, or may be operated byother computing devices (not shown in FIG. 1) connected to primarydatabase server 110, secondary database server 130, and backup server145 via network 150.

Secondary database server 130 may be a management server, a web server,a mobile computing device, or any other electronic device or computingsystem capable of receiving and sending data, and performingcomputer-readable program instructions. In other embodiments, secondarydatabase server 130 may represent a server computing system utilizingmultiple computers as a server system, such as in a cloud computingenvironment. In another embodiment, secondary database server 130 may bea laptop computer, a tablet computer, a netbook computer, a personalcomputer (PC), a desktop computer, or any programmable electronic devicecapable of communicating with primary database server 110 and backupserver 145, via network 150. In another embodiment, secondary databaseserver 130 represents a computing system utilizing clustered computersand components (e.g., database server computer, application servercomputers, etc.) that act as a single pool of seamless resources whenaccessed within distributed computer processing environment 100.Secondary database server 130 may include internal and external hardwarecomponents, as depicted and described with reference to FIG. 5.

Primary database 125 is the primary source database to which allreceived transactions are applied. Primary database 125 differs fromsecondary database 140 only by the transactions that have been appliedto primary database 125, but have not yet been sent to secondarydatabase server 130 and applied to secondary database 140. Transactionsreceived by primary database server 110 are applied substantiallyimmediately to primary database 125, whereas secondary database 140 isupdated with transactions subsequent to receiving a transaction log thatcontains a capacity level of transactions, such as transaction log 162,being sent to secondary database server 130 and applied to secondarydatabase 140.

Primary storage hardware 120 is connected to primary database server110, and includes primary database 125. Primary storage hardware 120includes storage and computing processor components that supporttransaction log updates from primary database server 110 to primarydatabase 125. Primary storage hardware 120 receives transaction updatesfrom primary database server 110, for example, the transactions oftransaction log 166, which are applied to primary database 125. Primarystorage hardware 120 is enabled to generate a snapshot of primarydatabase 125 in response to receiving instructions to do so from primarydatabase server 110, and is enabled to generate a second snapshot fromthe first snapshot, and make the first snapshot and second snapshotavailable to primary database server 110 and secondary database server130, respectively. Primary storage hardware 120 may include internal andexternal computer components, described in more detail with respect toFIG. 5.

In embodiments of the present invention, a snapshot of primary database125 is generated by primary storage hardware 120. A snapshot is aread-only, static view of a source database. A database snapshot isconsistent with the transactions applied to the source database as ofthe moment in time at which the snapshot is generated. Use of a snapshotin generating a backup copy of primary database 125 allows continuationof transaction updates without impact to high-availability systems. Thetime needed to generate a snapshot does not significantly increase withthe size of the data set, whereas by contrast, the time required togenerate a direct backup of data is proportional to the size of the dataset.

Primary database 110 receives live transactions 160 from users externalto distributed computer processing environment 100. Primary database 110receives and sends the transactions to primary storage hardware 120,which applies the updates to primary database 125. Primary databaseserver 110 is depicted as including transaction log 166. In oneembodiment of the present invention, live transactions 160, received byprimary database server 110, are written to transaction log 166, andthen applied to primary database 125 via primary storage hardware 120.Live transactions 160 continue to be written to transaction log 166until a pre-determined memory capacity is attained. The transaction logcontaining a full capacity of transactions, such as transaction log 164,is sent from primary database server 110 to secondary database server130, to be applied to secondary database 140.

In one embodiment of the present invention, primary database server 110sends instructions from transfer backup program 200 to secondarydatabase server 130 running on primary database server 110, to continuegenerating a backup copy of primary database 125, based on the redundantcopy of data in secondary database 140, in the event of an interruptionor failure associated with primary database 110. In another embodimentof the present invention, to more efficiently generate a backup copy ofdatabase data, primary database server 110 sends instructions fromsimultaneous backup program 300 to secondary database server 130, togenerate a backup copy of secondary database 140, which is a copy ofprimary database 125, except for the most recent transactions that havenot yet been sent to secondary database server 130 and applied tosecondary database 140. In this embodiment, primary database server 110generates a copy of the transaction log, which is less demanding ofprocessing time and allows primary database server 110 to maintain highavailability while a backup copy is performed.

Primary database server 110 may be a management server, a web server, amobile computing device, or any other electronic device or computingsystem capable of receiving and sending data, and performingcomputer-readable program instructions. In other embodiments, primarydatabase server 110 may represent a server computing system utilizingmultiple computers as a server system, such as in a cloud computingenvironment. In another embodiment, primary database server 110 may be alaptop computer, a tablet computer, a netbook computer, a personalcomputer (PC), a desktop computer, or any programmable electronic devicecapable of communicating with secondary database server 130 and backupserver 145, via network 150. In another embodiment, primary databaseserver 110 represents a computing system utilizing clustered computersand components (e.g., database server computer, application servercomputers, etc.) that act as a single pool of seamless resources whenaccessed within distributed computer processing environment 100. Primarydatabase server 110 may include internal and external hardwarecomponents, as depicted and described with reference to FIG. 5.

In an embodiment of the present invention, primary database server 110is depicted as hosting transfer backup program 200, simultaneous backupprogram 300, and parallel backup program 400. In other embodiments,primary database server 110 operates transfer backup program 200,simultaneous backup program 300, and parallel backup program 400, byaccessing programs 200, 300, and 400, via network 150. Transfer backupprogram 200 includes instructions that enable secondary database server130 to continue generating a backup copy of the aggregate transactionlog, using secondary database 140 as a passive copy of primary database125, because it does not directly service users. Secondary database 140is also known as a replica of primary database 125. Secondary database140, includes a copy of all the data of primary database 125 and ismaintained in a standby mode. In the event of an interruption or failureby primary database server 110 during generation of a backup copy of theaggregate transaction log, secondary database server 130 continues thegeneration of the aggregate transaction log backup.

Simultaneous backup program 300 includes instructions for secondarydatabase server 130 to generate a backup copy of secondary database 140,and instructions for primary database server 110 to simultaneouslygenerate a backup copy of the aggregate transaction log. Directing thegeneration of a backup copy of the database and aggregate transactionlog in this manner, maintains a high level of availability of primarydatabase server 110 to continue to receive transactions and updateprimary database 125, because generating a backup of the aggregatetransaction log requires less processing time and resources thangenerating a backup copy of the data file of the primary database.

In an example embodiment of the present invention, parallel backupprogram 400 includes instructions for primary storage hardware 120 togenerate a snapshot of primary database 125, and generate a copy of thesnapshot, producing two identical snapshots of primary database 125.Parallel backup program 400 directs primary database server 110 andsecondary database server 130 to use respective copies of the snapshotsfrom which each server generates a portion of a backup copy of primarydatabase 125. The combination of the portions results in a completebackup copy of primary database 125 at its state when the snapshots weregenerated. Parallel backup program 400 also includes instructions forgenerating a first snapshot of the aggregate transaction log, and asecond snapshot of the aggregate transaction log, based on the firstsnapshot. The snapshots are made available to primary database server110 and secondary database server 130, and are used by each server togenerate a portion of the transaction logs. The combination of theportions of the transaction logs results in a complete copy of thetransaction logs. Parallel backup program 400 directs primary databaseserver 110 and secondary database server 130 to send their respectiveportions of the backup copy to backup server 145, via network 150. Byusing snapshots of the data to be backed up, and dividing the workloadof generating the backup copies between primary database server 110 andsecondary database server 130, the backup will be completed morequickly, and primary database server 110 retains higher performance andremains more available to receive transactions, write the transactionsto a transaction log, and have transactions applied to primary database125. It should be pointed out that the backup processing described aboveis shared between two computing devices, primary database server 110 andsecondary database server 130, to illustrate the performanceefficiencies gained by sharing the backup operation. Embodiments of thepresent invention recognize that the processing of backup files may beshared across a plurality of servers, and is not limited to use of onlytwo servers.

In one embodiment of the present invention, parallel backup program 400divides the portions of the backup copy evenly between primary databaseserver 110 and secondary database server 130. In this case the entireamount of data to be backed up, for example “N” amount of data records,is divided so that, for example, records 0-N/2 are backed up by primarydatabase server 110, and data records (N/2+1)-N are backed up bysecondary database server 130. In another embodiment of the presentinvention, the portions of the data to be backed up are unevenly sharedbetween primary database server 110 and secondary database server 130.For example, 30% of the data may be backed up by primary database server110 and 70% of the data may be backed up by secondary database server130, both servers reading data from their respective snapshot of primarydatabase 125. In yet another embodiment, the backup of data is sharedacross a plurality of computing devices, with each device generating aportion of the backup file, and the combination of the portions of thebackup file performed by each of the plurality of computing devices,results in an aggregate backup file.

FIG. 2 is a flowchart of transfer backup program 200, in accordance toan embodiment of the present invention. If the backup copy of primarydatabase 125 by primary database server 110 is interrupted due, forexample, to a network failure or server error, and the database filebackup is not fully complete, the portion of the backup processed up tothe point of interruption is lost, and the backup of the database fileneeds to be repeated. In one embodiment of the present invention, if afailure occurs during the backup of the primary database file,instructions sent from transfer backup program 200 to backup server 145at the beginning of the backup process, instruct backup server 145 tosend an instruction to secondary database server 130 to re-initiate thegeneration of the backup and to send the backup data to backup server145. However, if the interruption of the backup copy occurs during thebackup of the transaction log, the backup generation is transferred tosecondary database 130.

Transfer backup program 200 supports the backup of transaction logs thathave not been completely backed up due to an interruption, for example anetwork failure or a server crash. Receiving an instruction to generatea backup of primary database 125 and the associated transaction logs,transfer backup program 200 begins backup of the database file and sendsinstructions to secondary database server 130 and/or backup server 145(step 210). In one embodiment, interruption of the transaction logbackup copy is determined by backup server 145 failing to receive backupdata after an initiation message received from primary database server110 and prior to receiving a completion confirmation. The instructionsfrom transfer backup program 200 directs backup server 145 to takeactions if a predetermined length of time is exceeded in which primarydatabase server 110 fails to send backup data to backup server 145. Forexample, backup of primary database 125 is initiated and transfer backupprogram 200 sends instructions to backup server 145. The instructionssent to backup server 145 direct backup server 145 to take action if apre-determined amount of time transpires without backup server 145receiving backup data from primary database server 110.

Transfer backup program 200 monitors the generation of the backup copyof the database file and the transaction log, and determines the startof the transaction log backup on the primary database server (step 220).Transfer backup program 200 determines that the backup of thetransaction logs has started, and backup data is being sent to backupserver 145.

Having determined the transaction log backup copy has started, aninterruption of the transaction log backup is determined based oninstructions previously sent by transfer backup program 200, to backupserver 145. The instructions determine if there is an interruption ofthe backup of transaction logs from primary database server 110(decision step 230). If no interruption is determined by backup server145 (step 230, “NO” branch), backup continues (step 260). Determiningthat the receipt of transaction log backup data is interrupted (step230, “YES” branch), the instructions received from transfer backupprogram 200 direct backup server 145 to determine if the backup of thetransaction logs resumes (decision step 240).

For example, backup server 145 determines the receipt of the backup datafrom the transaction logs of primary database server 110. Backup server145 determines if the aggregate transaction log backup copy from primarydatabase server 110 is interrupted. An exemplary, but non-exhaustivelist of events that may result in the interruption of the backup andsending of transaction log data to backup server 145 include, a failureassociated with network 150, an error associated with primary databaseserver 110, or a crash of primary database server 110.

Having determined that the backup data from primary database server 110has been interrupted, transfer backup program 200 direct backup server145 to determine if the backup of the transaction logs resumes within apre-determined time period, for example a time period that may rangefrom 10 seconds to 4 minutes. The pre-determined time period may be setbased on the impact of delay on the backup of the transaction log.Backup server 145 determines if the backup of the transaction logs hasresumed, by monitoring transaction rates, or determining a duration oftime associated with an interruption, for example. If the interruptionends and the aggregate transaction log backup resumes within apre-determined length of time, (step 240, “YES” branch), then backupprocessing of the aggregate transaction log continues (step 260).

If the interruption of transaction log backup data persists, and backupserver 145 determines the interruption to exceed a pre-determined lengthof time, transfer backup program 200 directs backup server 145 to sendan instruction to secondary database server 130 to continue backup ofthe aggregate transaction log beginning with the next transaction log inthe sequence (step 250). Backup server 145 monitors the length of timeassociated with the interruption of data received from primary databaseserver 110 generating a backup of the aggregate transaction log. If thelength of the interruption exceeds a pre-determined length of time, forexample 30 seconds, then the instructions received from transfer backupprogram 200 direct backup server 145 to send a signal or message tosecondary database server 130 to continue the backup generation of theaggregate transaction log, beginning with the transaction following thelast transaction of the sequence of transactions received by backupserver 145. For example, the pre-determined length of time for theinterruption may be a time within a range of 10 seconds to 4 minutes.

For example, backup server 145, directed by transfer backup program 200,determines that there is an interruption of transaction log backup datafrom primary database server 110 that exceeds a pre-determined length oftime of 30 seconds, and backup server 145 sends a message to secondarydatabase server 130 to continue the backup of the aggregate transactionlog. Secondary database server has received all transaction logs fromprimary database server, with the exception of the most recenttransaction log, for example, transaction log 166 (FIG. 1), which hasnot reached a capacity level of transactions. Instructions received bysecondary database server 130, from transfer backup program 200, directserver 130 to continue the generation of the aggregate transaction logbackup, beginning with the transaction subsequent to the lasttransaction of the transaction log sequence received by backup server145. For example, transaction sequence number E010000000C8.log, is thenext transaction in the sequence which follows the last receivedtransaction number sequence, which is sequence E01000000C7.log.

Having directed the secondary database server to continue generating theaggregate transaction log backup, beginning at the transaction sequencefollowing the last sequence received, backup continues (step 260). Thebackup of the aggregate transaction log continues from the transactionsequence following the last transaction sequence received by backupserver 145.

FIG. 3 is a flowchart illustrating operational steps of simultaneousbackup program 300, operating on primary database server 110 withindistributed computer processing environment 100 of FIG. 1, in accordancewith an embodiment of the present invention. In embodiments of thepresent invention, simultaneous backup program 300 performs theoperations of generating a backup copy of the database data file andgenerating a backup copy of the aggregate transaction log, dividing thebackup copying between both the primary database server and secondarydatabase server of FIG. 1. By splitting the workload of generating thebackup copies, the time to complete the backup copies is reduced, and byassigning the (typically) smaller transaction log to the primarydatabase server that receives and processes live transactions, theinterruption or performance loss of the primary database server isreduced. A benefit of simultaneous backup program 300 is that the backupcopies of the transaction log and the data file for primary database 125can be generated substantially simultaneous, such that the backup copiesof the data file and the transaction log may be initiated within aperiod of three seconds or less of each other. However, the completionof the backup copies may differ by a larger time period, depending onthe relative sizes of the data file and the transaction log, thereforethe time of completion for the respective backup copies may besignificantly greater than three seconds or less. In one embodiment ofthe present invention, the transaction log is designated to be run onthe primary database server, due to the size of a transaction log of adatabase typically being smaller than the size of a data file of thedatabase.

Simultaneous backup program 300 receives an instruction to perform abackup of the database (step 305). The backup of the database, such asprimary database 125 or replica secondary database 140, includesgenerating a backup copy of the data file and the aggregate transactionlog. Receiving the instruction, simultaneous backup program 300 preparesto execute a backup of the database.

In one embodiment of the present invention, before the backup isinitiated, simultaneous backup program 300 directs the primary storagehardware (primary storage server) to generate snapshots of the primarydatabase file and the transaction logs of the primary database server(step 310). The snapshots provide a read-only static copy of the primarydatabase file and transaction logs, respectively. The use of snapshotsallows the receipt of transactions, writing transactions to thetransaction logs, and updates to the primary database file, withoutinterruption or significant delays.

For example, simultaneous backup program 300 sends an instruction toprimary storage hardware 120 to generate a snapshot of the database fileof primary database 125, and a snapshot of the aggregate transaction logof primary database 125. The snapshots are made available to primarydatabase server 110 and secondary database server 130. In anotherembodiment of the present invention, simultaneous backup program 300directs primary database server 110 to create a snapshot of the primarydatabase, and to create a snapshot of the snapshot. The snapshotsinclude identical data states of the primary database and are used asread-only copies of the database data to perform backup copy generation.In yet other embodiments, simultaneous backup program 300 directssecondary storage hardware 135 to create a snapshot of secondarydatabase 140, and to create a snapshot of a snapshot, to be used asidentical copies of the secondary database, which is a replica of theprimary database. The snapshots created from the secondary database areused to generate a backup copy of the database.

Simultaneous backup program 300 initiates the backup of the aggregatetransaction log on the primary database server (step 320). The backup ofthe aggregate transaction log is generated by the primary databaseserver, using the snapshot of the transaction logs, which is generatedby the primary storage hardware. The backup copy of the aggregatetransaction log is sent to the backup server, typically positioned at alocation different from the primary and secondary database servers andthe primary and secondary databases.

For example, simultaneous backup program 300 sends an instruction toprimary database server 110 to initiate a backup copy of the aggregatetransaction log of primary database 125, using the snapshot of theaggregate transaction log generated by primary storage hardware 120 as areference. Primary database server 110 continues to receive transactionsto be applied to primary database 125, so assigning the backup of theaggregate transaction log, which is generally smaller in size than thedatabase file, maintains a high level of availability and performancefor primary database server 110 during the generation of the backup copyof the aggregate transaction log. The backup copy is sent to backupserver 145.

Having initiated the backup of the aggregate transaction log,simultaneous backup program 300 sends a message to the secondarydatabase server to initiate the backup of the database file (step 330).In one embodiment of the present invention, the secondary databaseserver receives a message to initiate a backup copy of the primarydatabase data file, which directs the secondary database server to usethe snapshot of the data file as a reference to generate the backupcopy. In another embodiment, the secondary database server 130 initiatesa streaming backup of secondary database 140, which is a replica ofprimary database 125. The generation of a backup copy of the aggregatetransaction log is initiated on the primary database server andinstructions are sent to the secondary database server to initiate thegeneration of a backup copy of the data file of primary database. In oneembodiment of the present invention, this may result in the generationof the respective backup copies occurring in a substantiallysimultaneous time frame, in which the backup copies of the transactionlog and the data file of the primary database are initiated in threeseconds or less of each other, but each backup copy may be completed atsignificantly different points in time, depending on the relative sizeof the backup copies. It should be pointed out that although embodimentsof the present invention do not require simultaneous generation of therespective backup copies, simultaneous generation of backup copiesprovides efficiencies. Because the secondary database server does notreceive live transactions, there is no performance or availabilityimpact related to receiving live transactions by having secondarydatabase server perform the backup of the data file, which is typicallylarger than the aggregate transaction log.

For example, simultaneous backup program 300 sends an instruction tosecondary database server 130 to initiate the backup of the databasefile of primary database 125. Secondary database server 130 is directedto use the snapshot of primary database 125, which was generated byprimary storage hardware 120. Secondary database server 130 beginsgenerating the backup copy of the database file from the snapshot ofprimary database 125, and sends the backup copy data to backup server145.

It should be noted that embodiments of the present invention directingthe generation of the primary database backup to be performed bysecondary database server 130, are intended to minimize performance andavailability impacts to primary database server 110. By directing thebackup of the aggregate transaction log, which are typically smaller insize relative to the corresponding database data file, to the primarydatabase server, there is less resource demand to compete with theprocessing of live transactions, which the primary database servercontinues to receive during backup operations. In some embodiments ofthe present invention, directing the backup of the primary database datafile to the primary database server may result in little or no impact tothe performance and availability of the primary database server, basedon use of the snapshot of the primary database, and the demand of livetransactions on primary database server 110.

Simultaneous backup program 300 receives a response from the primarydatabase server and the secondary database server confirming the backupis complete (step 340). Simultaneous backup program 300 receives aconfirmation response from each of the primary database server and thesecondary database server, indicating that the respective backup copiesare complete and have been sent to the backup server. For example, aconfirmation response is received from primary database server 110 andsecondary database server 130, indicating that the aggregate transactionlog backup copy has been completed by primary database server 110, andthe backup copy of the data file of primary database 125 has beencompleted. The confirmation responses are received by simultaneousbackup program 300.

Having confirmation from the primary and secondary database servers thatthe respective backups are complete, simultaneous backup program 300sends a confirmation to the backup server that the backup operations arecomplete (step 350). For example, simultaneous backup program 300receives confirmation from primary database server 110 that theaggregate transaction log backup is complete, and receives confirmationfrom secondary database server 130 that the backup of the database fileof primary database 125 is complete. Simultaneous backup program 300sends a confirmation to backup server 145 that backup operations arecomplete.

Simultaneous backup program 300 receives a confirmation that the backupcopies of the database file and transaction logs are received and storedin the same designated storage space (step 360). For example,simultaneous backup program 300 sends a message to backup server 145confirming the completion of the backup of the transaction logs and thedatabase file of primary database 125. Simultaneous backup program 300receives a confirmation from backup server 145 that the backup copies ofthe transaction logs and the database file have been received and arestored in the same designated filespace, and simultaneous backup program300 ends. The backup operations performed by simultaneous backup program300 are completed more timely and efficiently than if all operationswere performed by a single server or if operations were performedsequentially.

FIG. 4 is a flowchart illustrating operational steps of parallel backupprogram 400, operating on a primary database server within thedistributed computer processing environment of FIG. 1, in accordancewith an embodiment of the present invention. In some embodiments of thepresent invention, parallel backup program 400 generates portions of abackup copy on each of a plurality of database servers. The backup copyis based on an initial snapshot of the primary database, making use of ahardware cascading snapshot capability. Each portion of the backup copyis generated by a separate server, using a subsequent snapshot of theinitial snapshot of the primary database, such that each snapshot usedin generating a portion of the backup copy is an exact duplicate of theinitial snapshot. The portions of the backup copy are generated in asubstantially parallel manner, and the combination of the generatedportions constitutes a complete backup copy. Generating portions of abackup copy across a plurality of servers, provides greater efficiency,and improves performance and availability of the primary database serverduring backup operations.

In the following description of parallel backup program 400, theparallel backup copy of the database data file and the aggregatetransaction log are described using two database servers and a backupserver; however, this description serves to represent examples ofembodiments of the present invention, and is not intended to limit orexclude the use of a more than two servers to generate and store backupcopies of data and transactions.

Parallel backup program 400 determines the size of the database file(step 410). Parallel backup program 400 offers efficiencies in backingup larger database files. Efficiencies realized may be proportional tothe size of the database file, and for smaller database file sizes, theefficiencies gained may not warrant use of parallel backup program 400.In one embodiment of the present invention, parallel backup program 400determines the size of the database file of primary database 125, to usethe database file size information in subsequent decision making. Inother embodiments of the present invention, the condition of otherattributes in addition to file size, such as analytics from previousbackups, may be used to determine if shared backup workload may providesignificant efficiencies. Other attribute analytics may includeinformation regarding network bandwidth and the number of backup copiesrequired.

Parallel backup program 400 determines if the database file size exceedsa threshold (decision step 420). Parallel backup program 400 comparesthe database file size to a pre-determined threshold of file size, whichhas been chosen for decision making of whether the backup of thedatabase file is performed by parallel backup program 400 or, forexample, by simultaneous backup program 300. Determining that the filesize does not exceed the pre-determined threshold of file size (step420, “NO” branch), parallel backup program 400 sends a message toinitiate simultaneous backup program 300 (step 490), and parallel backupprogram 400 ends. For example, if the file size of a database file isdetermined to be 50 megabytes (MB) and the pre-determined threshold offile size is set to 200 MB, then the database file does not exceed thepre-determined file size threshold and parallel backup program 400initiates simultaneous backup program 300 (FIG. 3), and ends.

Determining that the file size exceeds the pre-determined threshold offile size (step 420, “YES” branch), parallel backup program 400 sends aninstruction to the primary storage hardware to generate a snapshot ofthe data file of the primary database (step 430). The primary storagehardware performs operations on the primary database in response toreceived instructions. The primary storage hardware is enabled togenerate a snapshot of the database file of the primary database. Asnapshot of the primary database is a read-only copy that captures thestate of the data in the database file at the moment in time in whichthe snapshot is generated. In embodiments of the present invention, thesnapshot generated by the primary storage hardware may be accessed bythe primary database server and the secondary database server.

For example, parallel backup program 400 sends an instruction to primarystorage hardware 120 (FIG. 1), to generate a snapshot, hereafterreferred to as the first snapshot, of the database file of primarydatabase 125. The first snapshot is generated at a specific point intime designated by “T0”, and is accessible by primary storage hardware120, primary database server 110, and secondary database server 130.

Parallel backup program 400 sends an instruction to the primary storagehardware to generate a second snapshot from the first snapshot (step440). The primary storage hardware accesses the first snapshot andgenerates a second snapshot based on the first snapshot, which is alsoknown as a cascading snapshot, resulting in identical snapshots. Bothsnapshots are read-only static views of the database file of the primarydatabase, and are consistent with respect to committed transactions,with the primary database at the moment in time when the snapshot wasgenerated.

In another embodiment, the first snapshot generation may be performed bysecondary storage hardware 135, in which a snapshot is generated basedon the database file of secondary database 140. Secondary database 140is a copy of primary database 125 at the point in time when the lasttransaction log was sent from primary database server 110 to secondarydatabase server 130 and was applied to secondary database 140. Secondarystorage hardware 135 generates a second snapshot from the firstsnapshot, resulting in identical snapshots. Both the first and secondsnapshots are accessible to both primary database server 110 andsecondary database server 130.

Having generated a first snapshot from the primary database and a secondsnapshot from the first snap shot, parallel backup program 400 assignsone snapshot (T0) to the primary database server and assigns the othersnapshot (T0′) to the secondary database server (step 450). In oneembodiment of the present invention, the first snapshot is assigned tothe primary database server and provides a dedicated, static source ofthe primary database from which a portion of a backup copy is generatedby the primary database server. The second snapshot is assigned to thesecondary database server, which is identical to the first snapshot andprovides a consistent source for the secondary database server togenerate a remaining portion of the backup copy. For example, parallelbackup program 400 assigns the first snapshot (T0) to primary databaseserver 110, and assigns the second snapshot (T0′) to secondary databaseserver 130. Both servers use their respective snapshot as a reference togenerate a portion of a backup copy of the database file of primarydatabase 125, and the combination of the portions results in a completebackup copy, including all the data from the identical snapshots. Inanother embodiment, the first snapshot is assigned to secondary databaseserver 130 and the second snapshot is assigned to primary databaseserver 110.

Parallel backup program 400 instructs the primary database server togenerate a portion of the backup copy, and instructs the secondaryserver to generate the remaining portion of the backup copy (step 460).The primary database server and the secondary database server bothgenerate portions of the backup copy, in parallel, using the snapshotsas a consistent, static reference of the data in the primary database.The instructions from parallel backup program 400 indicate to eachserver the start and endpoint of their respective backup portion. In oneembodiment of the present invention, parallel backup program 400 dividesthe generation of the backup copy so that half of the backup copy isgenerated by the primary database server, and the other half of thebackup copy is generated by the secondary database server. In otherembodiments of the present invention, the division between the databaseservers generating the backup portions may not be equal, such as 30% ofthe backup copy generated by the primary database server, and 70% of thebackup copy generated by the secondary backup server.

Although the embodiments described in detail, herein, include sharinggeneration of backup copies between two computing devices, such asdatabase servers, other embodiment may generate backup copies utilizinga plurality of computing devices, greater than two.

For example, parallel backup program 400 instructs primary databaseserver 110 to begin a portion of the backup of primary database 125,using the first snapshot as a reference of the data, at the initialrecord. For a database file containing “N” records, parallel backupprogram 400 instructs primary database server 110 to complete its backupportion at the record corresponding to, or nearest to N/2. Parallelbackup program 400 instructs secondary database server 130 to begin theremaining portion of the backup of primary database 125, using thesecond snapshot as a reference, at the record subsequent to the lastrecord to be completed by primary database server 110, which may be therecord corresponding to N/2+1, for example. Secondary database server130 is instructed to complete its backup portion at the recordcorresponding to N, such that the combination of backup portionsgenerated by primary database server 110 and the backup portiongenerated by secondary database server 130 includes all records in thedatabase file of primary database 125, at the moment in time when thefirst snapshot was generated. Parallel backup program 400 instructsprimary database server 110 and secondary database server 130 to sendthe respective backup portion data to backup server 145. In oneembodiment of the present invention, the backup portions are stored onbackup server 145, such that restoring the portions in a correct orderis easily discerned, for example, by including the first record numberof each portion in the file name.

Parallel backup program 400 determines if a parallel backup of theaggregate transaction log is to be generated (decision step 470). Insome embodiments of the present invention, a backup copy of theaggregate transaction log may be generated by means of parallel backupprogram 400. The decision to generate a backup copy of the aggregatetransaction log may be a user selected setting, or may be based on thefile size of the aggregate transaction log (not depicted in FIG. 4), ormay be based on analytic information from performing prior backups.Determining that parallel backup of the aggregate transaction log are tobe generated (step 470, “YES” branch), parallel backup program 400 loopsto step 430 to send a message to primary database server 110 to generatea snapshot of the aggregate transaction log, and proceeds as describedabove, but with respect to the aggregate transaction log.

Parallel backup program 400 sends a message to the backup server whenbackup is complete (step 480). The backup portions are generated, andthe backup data is sent to the backup server. A confirmation of receiptmay be received from backup server, and in response to completion of thebackup copy portions being generated and sent to the backup server,parallel backup program 400 sends a message to the backup serveracknowledging the completion of the backup, and parallel backup program400 ends.

For example, primary database server 110 and secondary database server130 generate their respective portions of the backup copy and send thebackup data to backup server 145. Backup server 145 indicates toparallel backup program 400 that the backup portion data is beingreceived. Subsequent to the completion of generating and sending thebackup copy portions to backup server 145, parallel backup program 400sends a confirmation message to backup server 145 that the backup iscomplete, and parallel backup program 400 ends.

In some embodiments of the present invention, transfer backup program200, simultaneous backup program 300, and parallel backup program 400,may be operated by a workload computing device (not shown), which may bea computing device depicted in distributed computer processingenvironment 100, or a separate computing device not depicted, designatedto distribute the backup workload, which makes use of a snapshot of thedatabase and a snapshot of the snapshot, to generate backup copies ofthe aggregate transaction log and the data file, to perform respectiveoperational steps described above.

FIG. 5 depicts a block diagram of components of primary database server110, secondary database server 130, primary storage hardware 120,secondary storage hardware 135, and database server 500, which are allcapable of operating or executing instructions from, transfer backupprogram 200, simultaneous backup program 300, and parallel backupprogram 400, in accordance with an embodiment of the present invention.

It should be appreciated that FIG. 5 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Database server 500, primary database server 110, and secondary databaseserver 130, primary storage hardware 120, and secondary storage hardware135, include communications fabric 502, which provides communicationsbetween computer processor(s) 504, memory 506, persistent storage 508,communications unit 510, and input/output (I/O) interface(s) 512.Communications fabric 502 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 502 can beimplemented with one or more buses.

Memory 506 and persistent storage 508 are computer-readable storagemedia. In this embodiment, memory 506 includes random access memory(RAM) 514 and cache memory 516. In general, memory 506 can include anysuitable volatile or non-volatile computer-readable storage media.

Transfer backup program 200, simultaneous backup program 300, andparallel backup program 400, are stored in persistent storage 408 forexecution by one or more of the respective computer processors 504 viaone or more memories of memory 506. In this embodiment, persistentstorage 508 includes a magnetic hard disk drive. Alternatively, or inaddition to a magnetic hard disk drive, persistent storage 508 caninclude a solid state hard drive, a semiconductor storage device,read-only memory (ROM), erasable programmable read-only memory (EPROM),flash memory, or any other computer-readable storage media that iscapable of storing program instructions or digital information.

The media used by persistent storage 508 may also be removable. Forexample, a removable hard drive may be used for persistent storage 508.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer-readable storage medium that is also part of persistent storage408.

Communications unit 510, in these examples, provides for communicationswith other data processing systems or devices, including resources ofdistributed computer processing environment 100. In these examples,communications unit 510 includes one or more network interface cards.Communications unit 510 may provide communications through the use ofeither or both physical and wireless communications links. Transferbackup program 200, simultaneous backup program 300, and parallel backupprogram 400, may be downloaded to persistent storage 508 throughcommunications unit 510.

I/O interface(s) 512 allows for input and output of data with otherdevices that may be connected to primary database server 110, secondarydatabase server 130, primary storage hardware 120, secondary storagehardware 135, and database server 500. For example, I/O interface 512may provide a connection to external devices 518 such as a keyboard,keypad, a touch screen, and/or some other suitable input device. In someembodiments of the present invention, external devices 518 may includeprimary storage hardware 120, which includes primary database 125, andsecondary storage hardware 135, which includes secondary database 140.External devices 518 can also include portable computer-readable storagemedia such as, for example, thumb drives, portable optical or magneticdisks, and memory cards. Software and data used to practice embodimentsof the present invention, e.g., transfer backup program 200,simultaneous backup program 300, and parallel backup program 400, can bestored on such portable computer-readable storage media and can beloaded onto persistent storage 508 via I/O interface(s) 512. I/Ointerface(s) 512 also connect to a display 520.

Display 520 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method for generating a backup copy of adatabase, the method comprising: a primary computing device, generatinga first snapshot of a primary database and additional snapshots of theprimary database, wherein the additional snapshots are snapshots of thefirst snapshot, collectively creating a plurality of snapshots that eachrepresent the state of the stored data at the time of the generation ofthe first snapshot, which results in identical snapshots havingidentical states of data within each snapshot, and the plurality ofsnapshots are available to the primary computing device, a secondarycomputing device, and zero or more additional computing devices,communicatively connected to the primary database; in response toreceiving an instruction to initiate a backup copy of content of theprimary database, sending a snapshot of the plurality of snapshots,identical to the first snapshot, to the second computing device and tothe zero or more additional computing devices; the primary computingdevice generating a configurable first portion of a backup copy of thecontent of the primary database, based on a corresponding first portionof the first snapshot; the primary computing device determining one ormore configurable non-overlapping portions of the backup copy of thecontent of the primary database, designated for distribution to thesecond computing device and the zero or more computing devices, whereinthe one or more configurable non-overlapping portions exclude theconfigurable first portion, which enables workload splitting ofgeneration of the backup copy of the content of the primary database;the primary computing device directing the second computing device andthe zero or more computing devices to generate, respectively, aconfigurable portion of the backup copy of the content of the primarydatabase by parallel processing of respective configurable portions ofthe backup copy, based on a corresponding portion of the snapshot of theplurality of snapshots received from the primary database, wherein theconfigurable portion of the backup copy respectively generated inparallel by the second computing device and the zero or more computingdevices are non-overlapping portions of the backup copy, the combinationof configurable portions of the backup copy includes a complete backupcopy of the content of the primary database; and the primary computingdevice directing the second computing device and the zero or morecomputing devices to send their respective completed non-overlappingportion of the backup copy of the primary database to a backup computingdevice, wherein the backup copy of the primary database includes abackup copy of the data file of the primary database and a backup copyof a transaction log of the primary database.